Synk Help
Index

# Why is Synk still scanning even though ZeroScan is enabled?

ZeroScan begins to take effect on the second run. It has to know the state of the two folders, and be able to see every change made since then, both of which can only be done after one successful run.

If Synk scans after the second run, it is possible that the ZeroScan data for the script has been reset. This can happen for several reasons:

1. You changed the script's settings: Some settings (most obviously the folders being synchronized, but some others as well) can affect which information needs to be stored for ZeroScan to function. Therefore, the old ZeroScan data must be discarded when these settings change.
2. Your system has been rebooted: The Synk Helper can only hear about events that happen while it is running. As there is no guarantee that no changes have happened to the system before the Helper is launched after startup, ZeroScan must be reset for safety.
3. OS drops events: Sometimes, the OS gets so overloaded with events that it can't keep up and drops some. Fortunately, the OS informs the Helper that events have been dropped, so the Helper resets the ZeroScan records, as they're no longer valid. A message will be logged to the console when this happens.
4. The Helper quit running briefly: This can happen if you reinstall the Helper, or if (heaven forbid) the Helper crashed.

## See also

ZeroScan